GET_TYPE_FROM_VARNAME block
Short summary
Name |
|
→POU type |
|
Category |
Standard (non-safe), MemoryEnh, block with internal error diagnostic |
Conform to →IEC-standard |
not defined in IEC-standard |
Graphical interface |
|
Available since |
version 1.42.0 (for Neuron Power Engineer) and version 2.3.1791 of Neuron RTS max version 3.8.0 (for library |
Functionality
The block returns the data type of a variable. Enter its instance path in upper case at input NAME
. The data type is returned as UDINT
value.
Neuron recommends to call the GET_TYPE_FROM_VARNAME
block just once for the variable to request. On the one hand the time behavior might be unpredictable and on the other hand it might take longer to determine the data type.
Restrictions for the usage:
-
The requested variable must have been declared with an elementary data type or an array of these elementary data types. The elementary data types are:
REAL
,LREAL
,USINT
,UINT
,UDINT
,ULINT
,SINT
,INT
,DINT
,LINT
,TIME
,BOOL
,BYTE
,WORD
,DWORD
,LWORD
,STRING
,CHAR
,DATE_AND_TIME
,DATE
orTIME_OF_DAY
-
There must be an instance path for the requested variable. This means that the following variables cannot be requested:
-
variables in →functions
-
→in-out variables (
VAR_IN_OUT
)
-
-
The requested variable must writeable from each position of the application (i.e. within and outside of the POU in which the variable has been declared). This means that the following variables cannot be requested:
-
variables with the keyword
CONSTANT
-
→input variables (
VAR_INPUT
) -
→output variables (
VAR_OUTPUT
)
-
-
It is only allowed to use the call of the block on the right side of the assignment operator "
:=
" for →assignments.
Inputs, outputs, return value
|
Identifier |
Description |
|
---|---|---|---|
Inputs: |
|
|
instance path of the variable (in upper case) |
Outputs: |
|
|
length (= memory size) of the variable (in bytes) or |
|
|
state of the operation (result code):
|
|
Return value: |
– |
|
data type of the requested variable
|
Input EN
and output ENO
are available when →calling the block. See "Execution control: EN, ENO" for information on input EN
and output ENO
.
See:
-
"Blocks for safe logic" whether this block is supported for developing safety-relevant applications.
-
"Highlighting safe logic in the FBD-editor" for the effects when using the block as a block for safe logic.
Internal error diagnostic for block
The block checks whether one of the above restrictions is violated. In such an error case, the output ENO
of the block is set to value FALSE
(or an equivalent). Moreover, the output STATUS
returns the appropriate code (see the above table under STATUS
), the output LEN
returns the value 0
and the block itself returns 0
(as return value).
Example for usage within ST-editor
Exemplary usage of the GET_TYPE_FROM_VARNAME block |
---|
|
When creating your application within the ST-editor, enter a call of a block by typing the text as requested by the syntax or use Content Assist.